in the _o_b_j_e_c_t, _t_y_p_e, and _i_n_t_e_r_f_a_c_e fields.
The _l_o_c_a_t_i_o_n is a string in the format
_f_a_m_i_l_y::::_h_o_s_t[[[[_p_o_r_t]]]], where _f_a_m_i_l_y is an address fam-
ily, _h_o_s_t is a host name, and _p_o_r_t is a port
number. Possible values for _f_a_m_i_l_y include ddddddddssss
and iiiipppp. You can use a leading #### to indicate that
a host name is in the standard numeric form. For
example, ddddddddssss::::////////ssssaaaallllzzzzbbbbuuuurrrrgggg[[[[555511115555]]]], ddddddddssss::::####555577775555dddd....555544442222eeee[[[[444455552222]]]],
iiiipppp::::vvvviiiieeeennnnnnnnaaaa[[[[1111777755556666]]]], and iiiipppp::::####111199992222....5555....5555....5555[[[[1111777799991111]]]] are all
acceptable _l_o_c_a_t_i_o_n specifiers.
The _a_n_n_o_t_a_t_i_o_n is a string of up to 64 characters
annotating the entry. Use double quotation marks
to delimit a string that contains a space or con-
tains no characters. To embed a double quotation
mark in the string, precede it with a backslash.
The _f_l_a_g is either llllooooccccaaaallll (the default) or gggglllloooobbbbaaaallll,
indicating whether the entry should be marked for
local registration only or for registration in
both the LLB and GLB databases. The _f_l_a_g is a
field that is stored with the entry; it does not
affect where the entry is registered. The
sssseeeetttt____bbbbrrrrooookkkkeeeerrrr and uuuusssseeee____bbbbrrrrooookkkkeeeerrrr commands select the
specify gggglllloooobbbbaaaallll as the _b_r_o_k_e_r__s_w_i_t_c_h, sssseeeetttt____bbbbrrrrooookkkkeeeerrrr
sets the current GLB; otherwise, it sets the
current LLB. The _h_o_s_t is a string in the format
_f_a_m_i_l_y::::_h_o_s_t, where _f_a_m_i_l_y is an address family and
_h_o_s_t is a host name. Possible values for _f_a_m_i_l_y
include ddddddddssss and iiiipppp. You can use a leading #### to
indicate that a host name is in the standard
numeric form. For example, ddddddddssss::::////////lllliiiinnnnzzzz,
ddddddddssss::::####444499999999dddd....555599990000ffff, iiiipppp::::pppprrrraaaagggguuuueeee, and iiiipppp::::####111199992222....5555....5555....5555 are
all acceptable _h_o_s_t specifiers.
Issue uuuusssseeee____bbbbrrrrooookkkkeeeerrrr, not this command, to determine
_f_a_m_i_l_y::::_h_o_s_t[[[[_p_o_r_t]]]], where _f_a_m_i_l_y is an address fam-
ily, _h_o_s_t is a host name, and _p_o_r_t is a port
number. Possible values for _f_a_m_i_l_y include ddddddddssss
and iiiipppp. You can use a leading #### to indicate that
a host name is in the standard numeric form. For
example, ddddddddssss::::////////ssssaaaallllzzzzbbbbuuuurrrrgggg[[[[555511115555]]]], ddddddddssss::::####555577775555dddd....555544442222eeee[[[[444455552222]]]],
iiiipppp::::vvvviiiieeeennnnnnnnaaaa[[[[1111777755556666]]]], and iiiipppp::::####111199992222....5555....5555....5555[[[[1111777799991111]]]] are all
acceptable _l_o_c_a_t_i_o_n specifiers.
You can use an asterisk as a wildcard in the
_o_b_j_e_c_t, _t_y_p_e, and _i_n_t_e_r_f_a_c_e fields to match any
value for the field. Unless you have suppressed
queries by invoking llllbbbb____aaaaddddmmmmiiiinnnn with the ----nnnnqqqq option,
uuuunnnnrrrreeeeggggiiiisssstttteeeerrrr asks you whether to delete each match-
ing entry. A yyyy[eeeessss] response deletes the entry. A
nnnn[oooo] response leaves the entry in the database. A
gggg[oooo] response deletes all remaining database
entries that match, without your being queried. A
qqqq[uuuuiiiitttt] response terminates the uuuunnnnrrrreeeeggggiiiisssstttteeeerrrr opera-
